[DataFactory]Merge master 1217 #17361
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Use pre steps to determine record * Add TestMode setting * Simplify live test post steps to use TestMode for recording condition
…7091) Co-authored-by: Sima Zhu <[email protected]>
* Update readme * Update sdk/monitor/Microsoft.OpenTelemetry.Exporter.AzureMonitor/README.md Co-authored-by: Reiley Yang <[email protected]> Co-authored-by: Reiley Yang <[email protected]>
The focus of these changes is to correct a bug in the samples and to introduce an SDK-level overview, covering each of the libraries.
* Move entire docgeneration into common tools * Move docindex to common * Added the package replacement logic * Fixed on parameters * Fixed param * Change function to dash * Added regex on function * Added display name. * Update eng/common/docgeneration/Generate-DocIndex.ps1 Co-authored-by: Wes Haggard <[email protected]> * Deal with js * Add no new line args * revert some test changes * Need to default to the double quotes for JS regex * Update Generate-DocIndex.ps1 * Added the appTitle * type Co-authored-by: Sima Zhu <[email protected]> Co-authored-by: Sima Zhu <[email protected]> Co-authored-by: Wes Haggard <[email protected]>
…efaults (#17039) * Default to true when live test platform does not have SupportedClouds override * Fall back to empty location default for live tests * simplify null checks
…17016) * Adding Identity support for Patch Vault * Adding Release notes for the changes * Resolving the breaking changes by adding identity
* [FR] Update to 2.1-preview.2 with generation and recordings (#16462) * generation and recordings * missing tests * PR feedback * enable test * export-api * [FR] Add invoices functionality (#16522) * add invoices * pr feedback * export api * Update sdk/formrecognizer/Azure.AI.FormRecognizer/src/RecognizeInvoicesOperation.cs Co-authored-by: Krista Pratico <[email protected]> Co-authored-by: Krista Pratico <[email protected]> * [FR] Add documentation for invoices (#16659) * documentation * PR feedback * generation plus small fixes (#16787) * [FR] Expose code generated properties (#16841) * selection mark state order: * appearance * bounding box * content-type bmp * pages * update to 2.1-preview.2 * language (#16889) * added more test for copy feature (#16892) * enable receipt and bc (#17004) * remove bc workaround (#17025) * disable receipts, enable AAD, move to canada (#17119) Co-authored-by: Krista Pratico <[email protected]>
…17101) * Add EnablePartitioning to QueueProperties ctor; rename GetRawMessage * Revert test change * Port ATOM fix * fix * PR fb
* {Identity] Prototype TokenCache option to enable sharing cache across credentials and executions
* prototype updates
* adding client side user authentication samples
* adding persistent token cache options
* fix compilation issues
* adding token cache samples
* fix header
* reword
* updating API spec
* temporary fix for AzureStack eng bits
* workaround for MSA account
* ignore failure test cases temporarily
* update api sig
* update version
* update change log
* update version
* fix changelog
* fix msal cache
* update msal version
* removing AuthenticationTokenRecord workaround
* adding configuration to SharedTokenCacheCredential
* upgrading msal
* update snippet
* [Identity] prepare for 1.4.0-beta.1 release (#16021)
* Updating changelog for 1.4.0-beta.1 release
* updating MSAL dependency
* Increment package version after release of Azure.Identity (#16028)
* make AuthenticationRecord public
* making APIs public that got switched to internal in merge
* adressing PR feedback
* add tests for new STCC options
Co-authored-by: Erich(Renyong) Wang <[email protected]>
Co-authored-by: Azure SDK Bot <[email protected]>
The focus of these changes is to triage the test hangs in the live suite that seem to be related to the snippet smoke tests. This should unblock test runs while I continue to troubleshoot and locate the root cause.
Increment package version after release of Microsoft.Azure.ServiceBus
…properties (#17112) Co-authored-by: Dongwei Wang <[email protected]>
Co-authored-by: Dongwei Wang <[email protected]>
Increment package version after release of Azure.Analytics.Synapse.Spark
# Summary Adds a reference to [InheritDoc](https://www.nuget.org/packages/SauceControl.InheritDoc/) to replace all `/// <inheritdoc/>` comments with the actual comment content in the documentation xml produced by the build. This is a development-only dependency; it will not be deployed with or referenced by the libraries. Note this produces a lot of warnings for `<inheritdoc />` comments that need to be further refined with a `cref="somBaseType"` attribute. Some examples of this are included in this PR. Example for `Azure.Security.KeyVault.Administration.xml`: **Before** ```xml <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.Id"> <inheritdoc/> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.Value"> <inheritdoc/> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.HasCompleted"> <inheritdoc/> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.HasValue"> <inheritdoc/> </member> <member name="M:Azure.Security.KeyVault.Administration.RestoreOperation.GetRawResponse"> <inheritdoc/> </member> ``` **After** ```xml <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.Id"> <summary> Gets an ID representing the operation that can be used to poll for the status of the long-running operation. </summary> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.Value"> <summary> Final result of the long-running operation. </summary><remarks> This property can be accessed only after the operation completes successfully (HasValue is true). </remarks> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.HasCompleted"> <summary> Returns true if the long-running operation completed. </summary> </member> <member name="P:Azure.Security.KeyVault.Administration.RestoreOperation.HasValue"> <summary> Returns true if the long-running operation completed successfully and has produced final result (accessible by Value property). </summary> </member> <member name="M:Azure.Security.KeyVault.Administration.RestoreOperation.GetRawResponse"> <summary> The last HTTP response received from the server. </summary><remarks> The last response returned from the server during the lifecycle of this instance. An instance of Operation<typeparamref name="T" /> sends requests to a server in UpdateStatusAsync, UpdateStatus, and other methods. Responses from these requests can be accessed using GetRawResponse. </remarks> </member> ```
* pre-release checklist changes * update sample in readme
Increment package version after release of Azure.AI.FormRecognizer
Increment package version after release of Azure.Core.Amqp
* Fixed the docindex.yml and rename the files * Reset the mutated changes * Force checkout as the changes have already copied out * Minor changes for parameters * Update Generate-DocIndex.ps1 * Update Generate-DocIndex.ps1 * Update Generate-DocIndex.ps1 * Added function to common * Update Generate-DocIndex.ps1 Co-authored-by: Sima Zhu <[email protected]> Co-authored-by: Sima Zhu <[email protected]>
The default image should now have the .NET 5 available.
ghost
added
Azure.Core
Compute
App Configuration
The focus of these changes is to create the initial set of performance test scenarios for the v12.x (track two) Data Lake client library.
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
The focus of these changes is to fix the instructions for adding packages since there are references to API changes from the beta in the sample code.
* Created Initialcut at GA API version * Checkpoint * Checkpoint * Implemented most of the core attestation service APIs. * Implemented V1 of all of MAA API Surface * Converted TPM request and response to ReadOnlyMemory * Another round of API review feedback * Updated readme.md and changelog.md a small bit; corrected a couple of API review feedback items * Somehow nunit got added to the test dependencies; removed it * Added snippets to readme.md * Fixed typo in tests.yml; Fleshed out readme.md a bit * Use ClientSecretCredentials not DefaultProviderCredentials for tests * Two test classes were still flagged as being live * Ran Export-API.ps1 * Updated root cl for autorest * Updated session records * Added new SDK to ci.yml * Fixed several static analysis errors * Use TestEnvironment.Credential for credentials * Try a different way of generating the key * Updated session records * Updated session records with policy document that does not contain CRLF characters * Pull request feedback changes * Updated changelog * More Pull Request feedback * Added assert that the number of signing certificates is at least 1 * Use Argument.AssertNotNullOrEmpty instead of Argument.IsInRange for array check
It may take up to 5 minutes for RBAC (AAD) role assignments to replicate. This makes live tests flaky. The short term solution is to add "sleep" after test resources provisioning. Long term solution to be found here #17384
- Bump to eea7c0141c0b7ad9f66f8ba06560b549c6b3b014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.